Skip to content

docs: replace removed talosctl gen commands in Certificate Management - #936

Open
Iheanacho-ai wants to merge 1 commit into
siderolabs:mainfrom
Iheanacho-ai:talos-v1.15-cert-management
Open

Iheanacho-ai wants to merge 1 commit into
siderolabs:mainfrom
Iheanacho-ai:talos-v1.15-cert-management

Conversation

@Iheanacho-ai

@Iheanacho-ai Iheanacho-ai commented Nov 11, 2026 •

Copy link
Copy Markdown
Member

What

Replaces the removed talosctl gen commands on the v1.15 Certificate Management page.

Why

Talos 1.15 removes talosctl gen ca, gen crt, gen csr, gen key, and gen keypair. The "From control plane machine configuration" section used gen key, gen csr, and gen crt to create a client certificate, so its steps fail on Talos 1.15.

Change

  • Rewrote "From control plane machine configuration" to generate a new talosconfig with commands that exist in 1.15:
    1. talosctl gen secrets --from-controlplane-config controlplane.yaml -o secrets.yaml extracts a secrets bundle, including the Talos API CA.
    2. talosctl gen config --with-secrets secrets.yaml --output-types talosconfig generates the talosconfig, as in "From secrets bundle", which the section links to.
    3. talosctl --talosconfig talosconfig config endpoint sets the endpoints, which the generated file doesn't have.
  • Added a note that the secrets bundle holds every cluster secret.
  • Removed the manual yq and base64 CA extraction and the hand-edited talosconfig YAML.
  • Only v1.15 changed. Talos 1.14 still has the removed commands.

Testing

  • Ran: End to end on a Talos v1.15.0-beta.0 node on AWS (official AMI), with the v1.15.0-beta.0 talosctl. Starting from only controlplane.yaml, followed the three steps as written. The regenerated talosconfig authenticated against the node: talosctl version and talosctl get machineconfig (which needs os:admin) both succeeded. Before the config endpoint step it failed with failed to determine endpoints. The new client certificate has the os:admin role, is valid for one year, and is issued by the cluster's Talos API CA.
  • Where: Locally against the beta talosctl container image, and on one Talos v1.15.0-beta.0 EC2 instance (deleted after the test).
  • By: An agent (Claude Code), reviewed by me.
  • Filled from outside the page: Nothing.

@mintlify

mintlify Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Preview approval required

This pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit dd06ea2.

Approve preview

@Iheanacho-ai
Iheanacho-ai marked this pull request as draft November 11, 2026 09:50
@Iheanacho-ai
Iheanacho-ai marked this pull request as ready for review November 11, 2026 09:57
Talos 1.15 removes talosctl gen ca, crt, csr, key and keypair. Generate a
new talosconfig from the control plane configuration with talosctl gen
secrets --from-controlplane-config and talosctl gen config instead.

Signed-off-by: Amarachi Iheanacho <amarachi.iheanacho@siderolabs.com>
@Iheanacho-ai
Iheanacho-ai force-pushed the talos-v1.15-cert-management branch from eb8e556 to dd06ea2 Compare November 11, 2026 10:01
@github-actions

Copy link
Copy Markdown

📋 Automated documentation review

An automated pass runs on documentation changes in every PR. The items below are suggestions to consider — advisory, not a merge gate.

Reviewed commit dd06ea2 · 🔴 0 critical · 🟡 0 warning(s) · ⚪ 1 notice(s)

Nothing flagged at critical or warning level — see any notices inline.

Notices, and the reviewer's full report, are in the run's doc-accuracy-report artifact.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants